Method and system for automatically updating contact information within a contact database

ABSTRACT

A method is proposed for automatically updating and maintaining contact information for various contacts stored in a contact database without requiring an individual to manually update their contacts by using an automated reply process for the maintaining of contact information, as well as only requiring one individual to be a member of the service. Updating of the contacts with the automated reply process installed is more frequent.

This application claims priority from U.S. patent application Ser. No.10/773,958 filed Feb. 9, 2004, which in turn claims priority from U.S.patent application Ser. No. 09/741,828 filed Dec. 22, 2000 (now issuedto U.S. Pat. No. 6,701,348).

FIELD OF THE INVENTION

This invention relates to a method of updating, maintaining andverifying contact information for various contacts held in a databaseand more particularly to an automated method of maintaining the contactinformation fields within a contact database without requiring anindividual to manually update same.

BACKGROUND OF THE INVENTION

In the past, people have maintained contact lists on paper. Theproverbial “black book” is a good example of a list of individuals andtheir contact information. Unfortunately, it is not uncommon that uponattempting to contact someone one discovers that the information is nolonger accurate. This is of tremendous inconvenience, especially duringemergency or time limited situations. Unfortunately, the task ofmaintaining a large contact list current is often too onerous for thefew times one needs to contact each individual.

Therefore, whenever someone changes address, phone numbers or any otherpiece of contact information, there is a necessity for them to providetheir contacts with the most current contact data. Conventional methodsof accomplishing this task include sending updated information by email,via facsimile, or even by telephoning to contacts in an address book andmaking others aware that some information has changed and they need tomanually update their contact list, which is time consuming.

A service offering automated updating of electronic contact informationand ensuring most current contact information is offered by PeopleStreetthrough their World Wide Web site PeopleStreet.com. PeopleStreetaddresses the difficult task of enabling people to stay connected totheir many circles of contacts. The service provided by PeopleStreetmanages the personal information and provides a dynamic link to allpersonal and professional relationships. This is performed by providinga method for each user to update their own address book entry, therebyautomatically updating all the other user contacts of their new addressbook entry, wherever they may be.

Although the service that PeopleStreet provides does automate thistedious process, it does require that each party is a member of theservice. In this manner information is updated from and to all partiessubscribed to the service. This facilitates updating your personalinformation and being updated of others. A shortcoming of the method isthat members of the address book, which are not already subscribed,still have to manually inform the subscribed user of their updatedcontact information according to the prior art updating method.

Contact.com also offers a similar type of contact service, whichprovides for the exchange of personal information. Once again,subscribed users decide which of their contacts are privileged to whichinformation fields and as a result when the contact changes theirpersonal information all the other address books linked to the contactare updated. This form of service requires the information to be storedon a central storage system. Although security may be strictly enforced,there are still security concerns because all personal information isaccessible from outside the server.

It would be highly advantageous to provide a method for updating contactinformation in an automated fashion absent either security concerns ormandatory subscription to a service by each party within a given contactlist.

SUMMARY OF THE INVENTION

The present invention seeks to automate the task of maintaining an up todate electronic contact address book. Advantageously the invention onlyrequires membership by one user, enabling them to have their contactinformation automatically maintained. Provisions are made for anoptionally installed program on the contact computer system allowing forthe automatic maintenance of contact request messages sent from the userto the contacts such that contacts do not feel bombarded by the periodicmessages sent by the user to ascertain the validity of the contactinformation.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments of the invention will now be described inconjunction with the following drawings, in which:

FIG. 1 presents a simplified exemplary flow diagram of a methodaccording to the invention for updating contact information stored in anelectronic form.

FIG. 2A presents another exemplary flow diagram according to embodimentof the invention where the method for updating contact informationstored in an electronic form

FIG. 2B shows the typical known boxes for different contact informationentry.

FIG. 3A presents a simplified exemplary flow diagram according to anembodiment of the invention wherein the transmission medium is theInternet.

FIG. 3B simplified exemplary flow diagram according to an embodiment ofthe invention wherein the transmission medium is the Internet andcommunication between a user and a contact takes place via an Internetserver.

FIG. 4 presents an exemplary method of automatically replying to anupdate request according to an embodiment of the invention.

FIG. 5 shows an exemplary flow chart for updating the user contactdatabase obviating the use of a server.

FIG. 6 presents an exemplary flow diagram for a contact having anautomated reply process install updates whenever their contactinformation changes.

DETAILED DESCRIPTION OF THE INVENTION

Generally, according to the invention a method is provided forcommunicating between at least two parties for the exchange of personalcontact information in such a manner that only one party is activelysubscribed to the service and such that all of their electronic contactinformation is automatically updated. Thus, the need for split contactlists—those who are subscribed and those who are not—is obviated.

Referring to FIG. 1, a simplified flow diagram of a method according tothe invention for updating contact information stored in an electronicform as a contact management database 100 is shown. For example, acontact list is stored within a personal digital assistant in the formof an address, phone and email contact list. Typically, such a list isboth portable and conveniently accessible. Convenient access includesthe ability to search and group contacts within the list.

In order to update the contact list, the method is initiated at step 108by at least one user, referred to as “the user.” The address book set-upby the user typically contains the contact information of all thecontacts with which the user wishes to communicate. Preferably, thecontents of the user's address book reside with the user, without havingcopies of personal data or the personal data of others being stored on acentral server.

Upon initiating the method, a message is transmitted at step 101 to eachindividual within the contact list requesting updated contactinformation. Typically, the message includes current contact informationfor the recipient in order to allow the recipient to indicate that nochange has occurred. There are a number of possible outcomes to the stepof transmission detailed above resulting in contacts classified intothree groupings; valid contacts, suspect contacts and invalid contacts,as will be described in the three cases below. The outcome of thetransmission being determined analysis step 106.

First, the transmission may fail, as shown by “Transmission Failed”outcome from the analysis step 106. Preferably, the transmission isresent at step 105 to verify that the failure was not caused by atemporary problem. Upon determining that the failure was not caused by atemporary system problem through a predetermined number transmissionresends, the contact is noted as invalid since it is evident that thecontact information used is no longer current.

Second, the transmission is not responded to, as shown by “No Response”outcome from the analysis step 106. From analysis step 106 the processproceeds then to step 104 and initiates follow-up communications whichinvolves a repeated contact attempt, thereby returning the process tostep 101. After several contact attempts, and the transmission does notappear to fail, in which case it is assumed that the contact informationis correct. After a predetermined number of communication cycles,involving steps 101, 106 and 104, for which no response from the contactis noted.

Third, the transmission is responded to, as indicated by the “ResponseReceived” outcome from the analysis step 106. This response can beeither an indication that the contact information is unchanged, or thatit has changed. This type of contact is noted as a valid contact and thecontact information changes are automatically entered at step 107 withinthe contact list stored within the contact information database 100.

Typically, the step of automatically entering the updated contactinformation involves parsing the response to determine contactinformation therein. Once the contact information is determined, it iscompared to current contact information allowing the changes to bedetected and then, the changes are implemented. Of course, when theresponse is in a known format, the step of comparing the contactinformation is obviated.

Advantageously, the contact information is only updated when the userrequests an update, and as such, the user's information is not changedwithout their knowledge.

In FIG. 2A another embodiment of the invention is disclosed where themethod for updating contact information stored in an electronic form isshown. Upon initiating the method, step 210, a message is transmitted toeach individual within the contact list in step 201 requesting updatedcontact information by facsimile. Typically, the message includescurrent contact information for the recipient in order to allow therecipient to indicate that no change has occurred.

There are a number of possible outcomes to the step of transmission 201detailed above, the determination of which occurring at analysis step206. However the one of primary concern is the receipt of a reply, inthe case of a valid contact. This being denoted as the “ResponseReceived” outcome from the analysis step 206. The reply in thisexemplary flow-chart being a facsimile message. In order to update theuser contact list an electronic representation of this facsimile messageis produced in the form of an electronic image of the facsimile documentis generated at step 207. This electronic representation isautomatically parsed to detect contact information therein at step 208which is then automatically entered in appropriate fields in the user'scontact list portion of the contact information database 200.

Typically after sending of an electronic facsimile message a reply isgenerated by the receiving system indicative of a successfultransmission. However in some cases no form of reply is received fromthe contact system and the success of the transmission cannot beverified. As a result after some prescribed amount of time the facsimilemessage is resent to verify the contact information. If after aspecified number of facsimile transmission attempts there is still noindication of a successful transmission from the contact system thecontact is noted as suspect.

If an error reply is received from the contact system after transmissionof an update request message, the message is resent to make sure theerror was not caused by a system problem. After a predetermined numberof unsuccessful contact attempts the contact is noted as invalid.

For example, a form 250 such as that shown in FIG. 2B, is used withentry boxes 211 through 220 indicated for different contact information.As shown the form 250 comprises entry boxes “First Name” 211, “MiddleInitial” 212, and “Surname” 213 allowing the user to enter their nameinto the form 250. Next the form 250 comprises “Address Line” 214,“City” 215, “State/Province” 216, “Zip or Postal Code” 217, “Country”218 relating to the address of the user who's name was entered into thename fields 211 to 213. Parsing of these manually entered data inspecific boxes is well known in the art. Finally, the user enters theirphone number into the field “Phone” 219 and fax number into the “Fax”220.

Referring to FIG. 3A, a simplified flow diagram is shown wherein thetransmission medium is the Internet. In order to update the contactlist, a user initiates the method in step 311. Upon initiating themethod, an electronic message is transmitted to the electronic addressof each contact stored within a contact list in process 301. Once theelectronic message is received on the contact system the message isverified, at step 302, before further action. Typically, the electronicmessage includes a subject line indicating a request for contactinformation update as well as current contact information for therecipient in order to allow the recipient to indicate for conveniencethat no change has occurred when this is the case. Once verified thevalid electronic message is sent to the user in step 303. There are anumber of possible responses the user system may receive and each isdetailed below, based upon the determination made in analysis step 304.

A first possible response is as follows: the transmission may fail andresult in an undeliverable electronic message, represented by theoutcome “Transmission Failed”. In these cases, it is generally evidentfrom the electronic message received back that either the contactinformation used is no longer current or the failed message delivery wascaused by a temporary system or network problem. Preferably, when adelivery error occurs the electronic message is re-sent, step 309, toverify that the failure was not caused by a temporary problem. Upondetermining that the failure was not caused by a temporary systemproblem, for example by executing a predetermined number of transmissionresends, the contact is noted as invalid since it is evident that thecontact information used is no longer current.

A second possible response is as follows: the transmission is notresponded to but no electronic message delivery failure is noted, inwhich case it is assumed that the contact information has been receivedand is correct. Such an outcome being denoted by “No Response”. Ofcourse, this is not necessarily the case, and optionally for importantcontacts, a follow up communication is initiated in step 310 to verifythe information. Preferably, a request for client contact is providedafter a predetermined number of consecutive occurrences of this possibleresponse from a same contact. Optionally, such requests includeinformation relating to a previous attempt and indicating that noresponse had been received. As such the “No Response” outcome returnsfrom step 310 to the sending of a message to the contact 301, althoughnow the content of the message is adjusted to reflect the currentposition as indicated supra.

Typically in the second case there is no reply received from the contactwithin some predetermined time period. Perhaps the contact has no methodof automatically replying to the electronic message, an error hasoccurred during transmission, the messages have been filtered by a“spam” or content filter, or they have simply missed the message amongsttheir general electronic messages. After a predetermined number ofcommunications wherein no response from the contact occurs the contactis noted as being suspect and an indication is provided to the user totake different action and determine the problem with this contactinformation, step 312. Preferably, the indication is generated onlyafter a predetermined number of contact list update attempts with noresponse. This allows the above noted assumption that the contactinformation is correct to be verified at intervals when no other data isreceived from the contact.

In the third case a response to the transmitted electronic message isreceived, as indicated by “Response Received”. The response, in thisexemplary embodiment is transmitted electronically from the contact toan electronic address of the user. Accordingly, the received message isparsed in process 307 for validity, and as this message is received froma known contact it is noted as valid or not. An invalid response resultsin this exemplary flow with the process moving to step 306 and stopping.For a valid contact the process moves to step 308 wherein the message isinterpreted and when contact information within the message has changed,the user system automatically updates the contact list with the changesinto the contact information database 300.

Referring to FIG. 3B, a flow diagram is shown wherein the transmissionmedium is the Internet and communication between a user and a contacttakes place via an Internet server. In order to update the contact list,a user initiates the method at step 331. Upon initiating the method, anelectronic message is generated and sent in step 321, to an Internetserver that receives the electronic message in step 325. The Internetserver authenticates the electronic message in step 322 before furtheraction is taken. If verified, the server commences a process forupdating the contact list information. In the first step 323 the servertransmits a message to each electronic address of contacts within thecontact list. Typically, the electronic message includes a subject lineindicating a request for contact information update as well as currentcontact information for the recipient in order to allow the recipient toindicate for convenience that no change has occurred when this is thecase. There are a number of possible responses that the server mayreceive in step 324, and each is detailed below.

A first possible response is as follows: the transmission may fail andresult in an undeliverable electronic message. This denoted as the“Transmission Failed” outcome path from step 324. In these cases, it isevident that either the contact information used is no longer current orthe failed message delivery was caused by a temporary system or networkproblem. Preferably, when a delivery error occurs the process triggers arequest in step 329 for the electronic message to be re-sent. Thisachieved by returning the process to step 321 and allowing verificationas to whether or not the failure was caused by a temporary problem. Upondetermining that the failure was not caused by a temporary systemproblem through a predetermined number transmission resends, the contactis noted as invalid since it is evident that the contact informationused is no longer current.

A second possible response “No Response” is as follows: the transmissionis not responded to but no electronic message delivery failure is noted,in which case it is assumed that the contact information has beenreceived and is correct. Of course, this is not necessarily the case,and optionally for important contacts, a follow up communication isinitiated in step 330 to verify the information. From step 330 theprocess returns to step 321, wherein the contacting sequence repeats.Preferably, a request for client contact is provided after apredetermined number of consecutive occurrences of this possibleresponse from a same contact.

Typically in the second case there is no reply received from the contactwithin some predetermined time period. In this case the contact has nomethod of automatically replying to the electronic message or perhaps anerror has occurred during transmission. After a predetermined number ofcommunications with no response the contact is notified, in step 333that the contact is suspect. The indication prompts the user to takeaction and determine the problem with this contact information.Preferably, the indication is generated only after a predeterminednumber of contact list update attempts with no response. This allows theabove noted assumption that the contact information is correct to beverified at intervals when no other data is received from the contact.

In the third case a response to the transmitted electronic message isreceived, “Response Received”. The response is assumed to have beentransmitted electronically from the contact to an electronic address ofthe user and as a result the contact is noted as valid. Upon receipt ofthe response on the user system, step 331, the message is interpretedand when contact information within the message has changed, the usersystem automatically updates the contact list with the changes in step328. These changes in the contact information are then stored within thecustomer information database 300.

Advantageously, the contact information is only updated when the userrequests an update, and as such, the user's information is not changedwithout their knowledge, but alternatively the information is updatedwithout the user's knowledge.

In an embodiment, the user specifies at which time intervals toautomatically update their contact information. In a properlyfunctioning system with all of the contacts having a method ofautomatically responding to an update request the contact information ismaintained at intervals sufficiently short to ensure that it ismaintained most current at all times.

Clearly, such an embodiment would be obtrusive to each contact if ameans for automatically replying is not supported. Also, when anautomated reply process is available to each contact, the method is notobtrusive to the contacts and as such, is a convenient method forcontact data update.

Referring to FIG. 4, a method of automatically replying to an updaterequest is shown. For the purpose of automating the reply process, afirst time a contact is contacted in accordance with the method of FIGS.3A,B for updating of their contact information, attached to theelectronic message is an automated reply process for installation withintheir system. This process is optionally installed on the system by thecontact or another person. Of course, the contact, at their discretion,may choose not to install the automated reply process. Once installed,the automated reply process acts to intercept update request electronicmessages received so as to prevent an individual from feelinginconvenienced by future update requests.

Upon installation of the automated reply process, an indication of suchis provided to the user. Once such an indication is received, a flag isset on the user system indicating same. Optionally, future updaterequests are then transmitted at more frequent time intervals from theuser to the contact since the automated reply process has beeninstalled. Preferably these intervals are specifiable by the user.

In the exemplary flow of FIG. 4 the process step 323 of sending themessage to the contact is preceded by a decision step 404 wherein a flagsetting check establishes whether the message is sent in step 323 orwhether the message is sent in conjunction with an automated replyprocess in step 406.

The contacts provide their contact information to the automated replyprocess through known input/output processes. For example, a window isprovided with fill in boxes and the user fills in their contactinformation using a keyboard and a pointing device in the form of amouse. The automated reply process stores the information, preferably innon-volatile storage, and upon intercepting an update requesttransmitted from the server, the automated reply process transmits thestored contact information to the server in a known format. Using aknown format obviates a need to parse the received message since data iseasily extractable based on the known format.

Referring to FIG. 5, a method of updating the user contact database isshown obviating the use of a server. A user system transmits electronicmessages to systems associated with contacts contained in the user'scontact list. Typically, the electronic messages are sent to anelectronic address in the form of email message for each contact. Theelectronic messages request updated contact information. Here, a processsimilar to that described with reference to FIG. 4 is conducted but theuser system acts as the server and automatically updates informationstored therein. As such the Internet server step 325 and validity check322 are omitted from the exemplary flow of FIG. 5. The user is notifiedof any new contact information changes requiring update on theirelectronic contact database through the above process. In the case whenthe contact list is stored on a personal digital assistant (PDA), uponconnecting the PDA with the user system an option is available forupdating the user contact list.

The exemplary flow of FIG. 5 differs from that of FIG. 4 as uponvalidity of the received electronic message being made in step 327 theuser is prompted in step 507 with a request to store the old contactdata alongside the new contact data. An affirmative response results inthe process moving to step 505 wherein the old contact data is stored.Otherwise the process moves immediately to automatically updating thedatabase in step 328.

In FIG. 6 another embodiment of the invention is shown wherein thecontact has an automated reply process installed. The contact enterstheir contact information initially in step 601, updates their contactinformation whenever it changes in step 602. In accordance with themethod of FIG. 5, this is beneficial since it allows the automated replyprocess to reply automatically with updated contact information. Here,the automated reply process also, automatically, transmits the updatedcontact information to each contact within their contact list, step 603.This allows for each contact to maintain up to the minute contactinformation. Upon sending the electronic message in step 603 a flag isset in step 604, at which point the electronic message is actually sentfrom the users system in step 605 as opposed to simply being logged assent in their electronic mail application in step 603.

Having sent the electronic message the system monitors subsequentelectronic messages to determine in step 606 whether a successfultransmission occurred. Detection of an error in transmission returns theprocess to step 603 for a further attempt at delivering the message.Detecting a successful transmission in step 606 results in the processmoving to step 607 wherein the users contact management system isupdated. Of course, when each contact has an automated reply processinstalled, the electronic message containing the updated contactinformation is intercepted and the contact database on the contact'ssystem is automatically updated therewith. Thus, a user's system servestwo separate but related functions of polling contacts to ensureaccurate updated contact information and transmitting contactinformation updates relating to the user's contact information upon achange thereto. The installation of automated reply processes on eachsystem ensures that the entire contact database update process is fullytransparent to each user other than a need to enter the contactinformation when it changes.

In the above-described system a single user has an electronic contactlist with a number of electronic addresses of contacts stored within thelist. As more contacts are initiated the size of the user contact listincreases. Since each contact is prompted to use the contact updatesystem and since each contact has numerous other contacts, the systemgrows exponentially without requiring any contacts to use the system andwithout requiring subscription to a central server when a peer to peercontact update method is employed. Thus, beginning with a single user,communications to other users on their contact list and then users ontheir contact lists and so forth. As such, the system isself-advertising and self propagating. That said, the system is not likea virus since each individual to whom an update request message is senthas an option of inaction and the general system continues to functionpredictably. Thus, the overall system is always under the control ofparticipating users.

In another embodiment the invention also has the capability to, overtime, rebuild a user contact list, in the case when a user contact listis damaged. Having the auto reply process installed on the contactsystems results in a periodic electronic message sent from other contactsystems to the user system, each requesting an update of contactinformation. Receiving this message at the user system results in theautomated reply process storing the contact electronic address of thecontact in the user's contact list. At the time for automatic updatingof contacts stored in the user's contact list, the automated replyprocess transmits an electronic message to the electronic address of allcontacts stored within the user contact list. Receiving a reply messagefrom this contact results in the contact information being stored underthat contact profile in the user contact list. The user contact list nowcontains the contact information for one of the contacts, which had beenpreviously lost. Over time, as more update requests are communicatedbetween the contacts and the user, the auto reply process will alsoserve to rebuild the damaged user contact list.

Another embodiment of the invention also covers the exchange of morethan contact information between a user system and a contact system.Typically, the automated reply process takes care of the updating ofcontact information for both user and contact systems. However, the autoreply process can also be used for the updating of other data, forinstance electronic data files. The user indicates a filename they arelooking for and inputs this filename into the input process of theautomated reply process. The automated reply process sends out anelectronic message from the user system to contact systems with messagecontents indicating a request for the specific file. On the contactsystem the automated reply process traps and interprets the incomingelectronic message. In this case the message is requesting a specificelectronic data file. There are two possible reply messages from thecontact system. If the file is stored on the contact system then anelectronic message with the attached file is transmitted via theautomated reply process to the user system. Otherwise if the file wasnot found then a message indicative of such is sent to the user system.Clearly this form of information exchange between a user and theircontacts is useful for sending more than just contact information updaterequest messages. Preferably, a handshake is initiated when a file isfound thereby allowing the originating system to select a source for thefile when more than one system has a copy thereof. In this way, a singlefile is not transmitted from numerous other systems.

Advantageously no information about the contact is stored on any serverand the contact information only resides on the systems of the contactor the user.

Numerous other embodiments may be envisioned without departing from thespirit or scope of the invention.

1. A method for updating an electronic contact information databasecomprising: receiving an electronic mail message at a system of acontact by an electronic message application; intercepting theelectronic mail message by an automated reply filter cooperatively inexecution with the electronic mail message application prior to storagethereof within an inbox of the electronic mail message application;parsing information fields within the intercepted electronic mailmessage to determine that the electronic message is one of an updaterequest message and another message; providing other messages forstorage within the inbox; generating a new electronic message includingdata indicative of current contact information for the contact in replyto a determined update request message; and transmitting the generatednew electronic message via a communication network.
 2. A method forupdating an electronic contact information database as defined in claim1 wherein the new electronic message generated by the automated replyprocess comprises information retrieved from the memory accessible tothe automated reply process.
 3. A method for updating an electroniccontact information database as defined in claim 2 absent storing anelectronic update message within the inbox.
 4. A method for updating anelectronic contact information database as defined in claim 2 absentstoring the new electronic message within the outbox.
 5. A method forupdating an electronic contact information database as defined in claim1 comprising: providing updated contact information to a first system,the updated contact information relating to a user of the first system;transmitting an electronic message including the updated contactinformation to a second other system via an electronic communicationmedium; receiving the transmitted updated contact information at thesecond other system; automatically extracting from the received updatedcontact information contact information relating to the user of thefirst system; and, automatically updating the contact information of theuser of the first system within a contact database in dependence uponthe extracted information.
 6. A method for updating an electroniccontact information database as defined in claim 5 wherein the updatedcontact information is transmitted as an electronic message and whereinreceiving includes the following: receiving an electronic message at thesecond other system by an electronic message application; interceptingthe electronic message at the second other system by an automated replyfilter; parsing information fields within the intercepted electronicmessage to determine updated contact information therefrom; and,updating the electronic contact information database in dependence uponthe updated contact information.
 7. A method for updating an electroniccontact information database as defined in claim 6 wherein, updating theelectronic contact information database comprises changing contactinformation for the contact.
 8. A method for updating an electroniccontact information database as defined in claim 6 wherein, theelectronic contact information database comprises the electronic contactinformation database of the second other system.
 9. A method forupdating an electronic contact information database as defined in claim1 comprising: providing updated contact information to a first system,the updated contact information relating to a user of the first system;transmitting an electronic mail message including the updated contactinformation to a second other system via an electronic communicationmedium; receiving the transmitted updated contact information at thesecond other system; automatically extracting from the received updatedcontact information contact information relating to the user of thefirst system; and, automatically updating the contact information of theuser of the first system within a contact database in dependence uponthe extracted information.
 10. A method for updating an electroniccontact information database as defined in claim 9 wherein the updatedcontact information is transmitted as an electronic mail message andwherein receiving includes the following: receiving an electronic mailmessage at the second other system by an electronic mail messageapplication; intercepting the electronic mail message by an automatedreply filter cooperatively in execution with the electronic mail messageapplication prior to storage thereof within an inbox of the electronicmail message application; parsing information fields within theintercepted electronic mail message to determine that the electronicmail message is one of update contact information and another mailmessage; and, providing other mail messages for storage within theinbox.
 11. A method according to claim 9 wherein, updating the contactinformation of the user includes maintaining a history of contactinformation for the user.
 12. A method according to claim 1 wherein theelectronic mail message application is in execution on the system of thecontact; wherein the automated reply filter is in execution on thesystem of the contact; and, wherein the generated new electronic messageis transmitted from the system of the contact via the communicationnetwork.
 13. A method for updating an electronic contact informationdatabase comprising: providing updated contact information to a firstsystem, the updated contact information relating to a user of the firstsystem; transmitting an electronic mail message including the updatedcontact information to a second other system via an electroniccommunication medium; receiving the transmitted updated contactinformation at the second other system; automatically extracting fromthe received updated contact information contact information relating tothe user of the first system; and, automatically updating the contactinformation of the user of the first system within a contact database independence upon the extracted information.
 14. A method for updating anelectronic contact information database comprising: a) transmitting aplurality of electronic mail messages, each requesting in a humanintelligible form updated contact information, each electronic mailmessage transmitted to a contact destination of at least one contactfrom a plurality of contacts stored within the electronic contactinformation database; and b) receiving a return message relating to atleast one of the electronic mail messages and indicative of a change ofcontact information; and c) automatically updating the contactinformation database with the updated contact information.
 15. A methodaccording to claim 14 wherein, the human intelligible form comprises arequest in the English language for updated contact information.
 16. Amethod according to claim 14 wherein, the change of contact informationcomprises an invalid destination address and the return messagecomprises a failure notice.
 17. A method according to claim 14 wherein,the plurality of electronic mail messages are substantially similar. 18.A method according to claim 17 wherein, the plurality of electronic mailmessages are automatically generated.
 19. A method according to claim 14wherein, the plurality of electronic mail messages are automaticallygenerated in dependence upon a template message.
 20. A method accordingto claim 19 wherein, each of the plurality of electronic mail messagescomprises contact information of a contact destination thereof fordisplay within a body of the electronic mail message.
 21. A methodaccording to claim 14 wherein, the plurality of electronic mail messagesis transmitted at intervals.
 22. A method comprising: at intervalsgenerating in dependence upon a template a plurality of electronic mailmessages, each requesting in a human intelligible form updated contactinformation for a contact destination of at least one contact from aplurality of contacts stored within the electronic contact informationdatabase; each electronic mail message for transmission to the contactdestination.
 23. A method according to claim 22 wherein, each of theplurality of electronic mail messages comprises contact information ofthe contact destination thereof for display within a body of theelectronic mail message.
 24. A method for updating an electronic contactinformation database comprising: providing contact information relatingto an individual, the information relating to the individual andprovided to a computer of the individual; storing the contactinformation relating to the individual within a storage medium of asystem; initiating a process between the system and another system forproviding the contact information therebetween for use in updatingcontact information of one of the system and the another system.
 25. Amethod according to claim 24 wherein the contact information is providedby the individual.
 26. A method according to claim 24 wherein thecontact the information is provided in response to a request therefore.27. A method according to claim 26 wherein initiating comprisesproviding an email message.
 28. A method according to claim 24 whereinfirst system comprises the computer.
 29. A method according to claim 24wherein the contact information is provided to each of a plurality ofother systems during each of a plurality of processes.